Detailed Business Process Model Description : Meter Read Types

Meter Read Types
Meter reads with this value are entered by a billing administrator who wants to force billing to bill a customer for a given amount of consumption.
A meter reader using a handheld device records meter reads with this value. The handheld device deems a read as "verified" if the meter reader typed the same dial reading in twice. Some organizations have their handhelds programmed to require the double entry of dial readings when the entered value is outside normative values (i.e., the resultant consumption fails high / low checks).
A meter reader using a handheld device records meter reads with this value. See the description for "verified" above for the difference between a "regular" and a "verified" reading.
Meter reads with this value are created by the system automatically when prorating normal cycle-based reads for use with an off-cycle start service or stop service.
Meter reads with this value are informed guesses of consumption. These would be used when there was no real reading (i.e., a regular or verified reading), and the system was not allowed to estimate consumption (for whatever reason). This value is rarely used.
Meter reads with this value are estimates of consumption made by a 3rd party service provider, such as an MDMA, the distribution company, or an energy supply company.
The billing process creates meter reads with this value when a reading cannot be found and the service agreement allows estimation.
Meter reads with this value are entered to indicate that a read was purposefully not performed (for whatever reason - mad dog, nasty rose bush, deep snow, etc.). A read with this value is not a read at all; it's just an audit trail.

© 2011 Oracle and/or its affiliates. All Rights Reserved